Apply brand tone and writing style fixes#6303
Merged
Merged
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
ethanpalm
approved these changes
Jun 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Normalize punctuation in the static export overview so it matches the em dash style used elsewhere in the docs.
Changes
api/static-export/overview.mdx: replace--with—in the Authentication section.Context
The triggering PR introduced the client export feature pages. A quick style pass on the in-scope English pages (
api/static-export/*.mdx,deploy/export.mdx) found one punctuation inconsistency; voice, headings, terminology, and sentence length were already consistent.Note
Low Risk
Copy-only punctuation in documentation; no code or API behavior affected.
Overview
Aligns punctuation in the static export overview Authentication section with the docs’ em dash style.
In
api/static-export/overview.mdx, the phrase about server-side secrets now uses an em dash (—) instead of a double hyphen (--) before “do not expose them in client-side code.” No wording or behavior changes.Reviewed by Cursor Bugbot for commit d5ba2e2. Bugbot is set up for automated code reviews on this repo. Configure here.